Fix: CLI logs wrong path for utils file during init

Fixes the issue where the CLI incorrectly logs the default path for the utils file even when it's installed at a custom location.

Problem

When initializing shadcn-svelte with a custom path for the utils file (e.g., $lib/features/shared/components/_shadcn/utils instead of the default $lib/utils), the CLI displays that utils was installed at the default path even though it was actually placed in the correct custom location.

Example from the issue:

• User configures utils path: $lib/features/shared/components/_shadcn/utils
• File is correctly installed at: src/lib/features/shared/components/_shadcn/utils.ts
• But CLI incorrectly shows: ✔ utils installed at src/lib/utils

Root Cause

The display logic in packages/cli/src/utils/add-registry-items.ts calculates the displayed path differently from the actual file path:

• Actual file path: Calculated by resolveItemFilePath() which has special handling for "utils" item (lines 186-190 in registry/index.ts)
• Displayed path: Calculated by getItemAliasDir() + item name, which doesn't account for the special utils handling

Solution

Modified the display logic to track and use the actual file path that was written:

1. Track the first file path written in a new firstFilePath variable
2. For "utils" item specifically, use this tracked path for the display message
3. This ensures the displayed path matches the actual location where the file was installed

Changes

Modified Files:

• packages/cli/src/utils/add-registry-items.ts - Added 11 lines to track and display actual file path
• packages/cli/test/utils/add-registry-items.test.ts - Added 57 lines with new test case, fixed Windows path compatibility

Code Changes:

// Track the actual file path that was written
let firstFilePath: string | undefined;
for (const file of item.files) {
    let filePath = registry.resolveItemFilePath(opts.config, item, file);
    // ... write file ...
    if (!firstFilePath) {
        firstFilePath = filePath;
    }
}

// Use it for display
if (item.name === "utils" && firstFilePath) {
    const itemPath = path.relative(cwd, firstFilePath);
    return `${highlight(item.name)} installed at ${color.gray(itemPath)}`;
}

Testing

• ✅ All 147 tests passing (added 1 new test)
• ✅ TypeScript type checking passes
• ✅ Prettier formatting applied
• ✅ ESLint checks pass
• ✅ Test added for custom utils path scenario
• ✅ Fixed Windows test failure by normalizing paths with toPosixPath helper

Impact

• Minimal change: Only affects the display message for utils item
• No breaking changes: Actual file installation logic unchanged
• Backward compatible: Works with both default and custom paths
• Cross-platform: Tests now work on Windows, Linux, and macOS
• Improved UX: Users now see the correct path where utils was installed

Before & After

Before the fix:

✔ utils installed at src/lib/utils

(Even when installed at src/lib/features/shared/components/_shadcn/utils.ts)

After the fix:

✔ utils installed at src/lib/features/shared/components/_shadcn/utils.ts

(Shows the actual path where the file was installed)

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.